Restrict Attribute Creation Access

Is this possible? I have never tried to do it.
Issues:
If I remove the create access users are not going to be able to create objects. If I add the modify access users will be able to modify the description or module name and create baselines. OMG what should I do.
I was planning to create a trigger to allow users to open the modules only shareable edit, and allow exclusive edit access to only certain groups.

HELP!!!
SystemAdmin - Wed Apr 18 16:58:20 EDT 2012

Re: Restrict Attribute Creation Access
SystemAdmin - Wed Apr 18 17:33:42 EDT 2012

Well, I went to the formal.dxl and added the following routine...
User u = find(doorsname)
Group g = find("Administrative Group")
if(member(g,u)){
createMenuItem(Attributes...)
createMenuItem(Types...)
}

It seems to work. Have anyone had issues with modifying this file before?

Re: Restrict Attribute Creation Access
llandale - Thu Apr 19 12:27:50 EDT 2012

Its a little worse. If you provide only "R" to the module but then provide "RMCD" to all the top level objects, folks will not be able to open the module shared.

I think your trigger idea is rather excellent. I would make it a project level post-module-open trigger that checks the name against a list of restricted modules, and if so and mode is "Edit" then downgrade to "Shared".

-Louie

Re: Restrict Attribute Creation Access
llandale - Thu Apr 19 12:35:51 EDT 2012

llandale - Thu Apr 19 12:27:50 EDT 2012
Its a little worse. If you provide only "R" to the module but then provide "RMCD" to all the top level objects, folks will not be able to open the module shared.

I think your trigger idea is rather excellent. I would make it a project level post-module-open trigger that checks the name against a list of restricted modules, and if so and mode is "Edit" then downgrade to "Shared".

-Louie

I hate it when I start thinking. Perhaps the trigger checks for exactly "RC" access to the module, and deny Edit if so. Then you don't need a list of protected modules, and it seems to me that "RC" is so squirrely that it would be a reasonable flag to protect a module.

Protecting modules from clumsy folks has always been an Achilles Heal, I think you've stumbled into something rather useful.

-Louie

Re: Restrict Attribute Creation Access
SystemAdmin - Thu Apr 19 12:39:34 EDT 2012

llandale - Thu Apr 19 12:35:51 EDT 2012
I hate it when I start thinking. Perhaps the trigger checks for exactly "RC" access to the module, and deny Edit if so. Then you don't need a list of protected modules, and it seems to me that "RC" is so squirrely that it would be a reasonable flag to protect a module.

Protecting modules from clumsy folks has always been an Achilles Heal, I think you've stumbled into something rather useful.

-Louie

Louie, I posted something else, related manipulate the formal.dxl file. Read it an let me know what do you think.

Thanks for the other reponses.

Re: Restrict Attribute Creation Access
llandale - Thu Apr 19 13:06:58 EDT 2012

SystemAdmin - Wed Apr 18 17:33:42 EDT 2012
Well, I went to the formal.dxl and added the following routine...
User u = find(doorsname)
Group g = find("Administrative Group")
if(member(g,u)){
createMenuItem(Attributes...)
createMenuItem(Types...)
}

It seems to work. Have anyone had issues with modifying this file before?

While some other are in favor, I am not in favor of attempting to modify the installed files. In this case you need to find a way to get this new formal.dxl out to all the clients, and if its an important change someone can probably figure out what has happened and revert it.

-Louie